…ntime

Addresses the review finding that a single WebSocket failure was
terminal. Instead of extending the forked connection machinery, drop it
(~400 lines) and inherit the parent OpenAI plugin's
_main_task/_run_ws/_reconnect loop, xAI-style; Boson-specific behavior
now lives in small overrides and hooks:

- Reconnection follows the server's documented contract (the voice-chat
  server keeps no state across connections): the base _reconnect re-sends
  the full session config and replays the local chat-context mirror via
  conversation.item.create, with _create_session_update_event /
  _create_tools_update_event / _create_update_chat_ctx_events overridden
  to emit Boson-shaped payloads. Retry count/backoff come from
  conn_options, and a session_reconnected event is emitted on resume.
- _run_ws wraps the base loop only to reclassify closes a reconnect
  cannot fix as non-retryable: close code 3000 (invalid API key) and
  server-announced session ends (session.idle_timeout,
  session.max_duration_reached), which must not be resurrected.
- Boson-only server events are handled off the base's
  openai_server_event_received hook instead of a forked dispatch;
  _main_task fails pending response futures immediately on terminal
  failure instead of leaving them to their own timeouts.
- Stop advertising auto_tool_reply_generation: the server treats
  conversation.item.create as a pure insert now, so the framework must
  send response.create after tool outputs — previously tool calls
  completed client-side but no reply audio ever came back.
- Treat conversation.item.added for a known id as an in-place update:
  the server merges consecutive same-role turns into one item and
  re-emits added with cumulative content, which the base insert rejected
  ("already exists"), leaving the mirror with stale content.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

… ids

The server now stores client-supplied item ids and echoes them on
conversation.item.added (duplicate ids are rejected instead of merged), so
item ids work as the foreign key the base machinery expects. Drop the
append-only update_chat_ctx and its manual seen-id ledger in favor of the
base implementation: diff against the remote mirror, create/delete sync,
and echo-correlated futures.

_create_update_chat_ctx_events shrinks to a thin adapter: it feeds the base
diff a text-only mirror of the context (audio is represented by its
transcript; the GA converter must never see audio frames, whose conversion
can raise on empty buffers) and rebuilds each create with the Boson item
shape, mapping the unsupported "root" previous_item_id sentinel to a tail
append. A minimal extra="allow" item model keeps the base isinstance/echo
plumbing working without fighting the GA content-type literals.

With items addressable, mutable_chat_context returns to the base default
(True): interrupted never-played messages are now cleaned up server-side
and realtime sessions can be reused across agent handoffs.

Also trim nonstandard surface while here: drop the RealtimeModel.aclose
override that closed sessions (session lifecycle belongs to the framework)
and the _pending_response_futures test-compat alias, remove the unused
NUM_CHANNELS re-export and single-use helpers, warn once instead of
per-frame in push_video, and reword comments to describe wire behavior.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>